Method for network management based on NETCONF protocol, and associated network device

ABSTRACT

The present disclosure discloses a method used in a network device for network management based on NETwork CONFiguration (NETCONF) protocol, and an associated network device. The method includes: receiving a Remote Procedure Call (RPC) message from a network management system, the RPC message instructing the network device to perform an edit operation on the network device&#39;s configuration; generating a configuration change notification based on the received RPC message to indicate that the network device&#39;s configuration has changed, the configuration change notification indicating a target of the edit operation, a type of the edit operation, and a value of the edit operation; and transmitting the configuration change notification to the network management system.

This application is a 35 U.S.C. § 371 national phase filing ofInternational Application No. PCT/CN2016/099321, filed Sep. 19, 2016,the disclosure of which is incorporated herein by reference in itsentirety.

TECHNICAL FIELD

The present disclosure relates to network management, and moreparticularly, to a method used in a network device for networkmanagement based on NETwork CONFiguration (NETCONF) protocol, and theassociated network device.

BACKGROUND

This section is intended to provide a background to the variousembodiments of the technology described in this disclosure. Thedescription in this section may include concepts that could be pursued,but are not necessarily ones that have been previously conceived orpursued. Therefore, unless otherwise indicated herein, what is describedin this section is not prior art to the description and/or claims ofthis disclosure and is not admitted to be prior art by the mereinclusion in this section.

The NETCONF protocol is a network management protocol developed andstandardized by the Internet Engineering Task Force (IETF). It providesmechanisms to install, manipulate, and delete the configuration ofnetwork devices. Its operations are realized on top of a simple RemoteProcedure Call (RPC) layer. The NETCONF protocol uses an ExtensibleMarkup Language (XML) based data encoding for the configuration data aswell as the protocol messages. The protocol messages are exchanged ontop of a secure transport protocol.

The NETCONF protocol uses a simple RPC-based mechanism to facilitatecommunication between a client (also referred to as a NETCONF client)and a server (also referred to as a NETCONF server). The client can be ascript or application typically running as part of a network manager.The server is typically a network device. The terms “device” and“server” are used interchangeably in this document, as are “client” and“application”.

FIG. 1 illustrates a structure diagram of the NETCONF protocol. As shownin FIG. 1, the NETCONF protocol can be conceptually partitioned intofour layers: a Content layer, an Operations layer, a RPC layer and aTransport layer. The Transport layer provides a communication pathbetween a client and a server. The RPC layer provides a simple,transport-independent framing mechanism for encoding RPCs. TheOperations layer defines a set of base protocol operations to retrieveand edit the configuration data. The base operations may be invoked asRPC methods with XML-encoded parameters. The Content layer consists ofconfiguration data and notification data.

The NETCONF Data Modeling Language (NETMOD) Working Group has completedwork to define a “human-friendly” modeling language for defining thesemantics of operational data, configuration data, notifications, andoperations, called YANG. YANG is defined in RFC 6020, and is accompaniedby the “Common YANG Data Types” found in RFC 6021. YANG is a datamodeling language used to model configuration and state data manipulatedby the NETCONF protocol, NETCONF remote procedure calls, and NETCONFnotifications.

A Yang module has been defined to allow a NETCONF client to receivenotifications for some common system events. The YANG module specifies asmall number of event notification messages for use within the ‘NETCONF’stream, and accessible to clients via the subscription mechanismdescribed in [RFC5277].

These notifications pertain to configuration and monitoring portions ofthe managed system, not the entire system. A server MUST report eventsthat are directly related to the NETCONF protocol. A server MAY reportevents for non-NETCONF management sessions, using the ‘session-id’ valueof zero. This module defines a notification (i.e., the“netconf-config-change” notification) for the ‘NETCONF’ stream to notifya client application that the NETCONF server state has changed. The“netconf-config-change” notification is generated when the NETCONFserver detects that the server capabilities have changed, and indicateswhich capabilities have been added, deleted, and/or modified.

FIG. 2 depicts a tree structure of the “netconf-config-change”notification. Event type itself indicates that the system configurationhas changed. This event could alert an attacker that specificconfiguration data nodes have been altered.

As shown in FIG. 2, the “netconf-config-change” notification may havethree elements, i.e., “changed-by”, “datastore” and “edit”. The“changed-by” element may indicate whether the server or a specific usermanagement session made the configuration change, and identify the username, session-id, and source host address associated with theconfiguration change, if any. The “datastore” element may indicate whichdatastore has been changed. This data can be used to determine if thenon-volatile startup configuration data has been changed. The “edit”element identifies the specific edit operations and specific datastoresubtree(s) that have changed. This data could be used to determine ifspecific server vulnerabilities may now be present.

As illustrated in FIG. 2, the “edit” element contains two leaves, i.e.,target and operation. No leaf is defined for its value. So, from the“netconf-config-change” notification, the user can only know which nodeis changed and what the operation is. But, the user can't know the valueconfigured to. If the user wants to know what value is configured,he/she has to send another RPC message to get the node's value indatastore.

SUMMARY

It is an object of the present disclosure to provide a method to add anew leaf “value” by augmenting the “edit” element, so that the“netconf-config-change” notification contains all the necessaryinformation for an edit operation: a target of the edit operation, atype of the edit operation, and a value of the edit operation (i.e., avalue configured for the edit operation).

In a first aspect, a method used in a network device for networkmanagement based on NETCONF protocol. The method includes: receiving aRPC message from a network management system, the RPC messageinstructing the network device to perform an edit operation on thenetwork device's configuration; generating a configuration changenotification based on the received RPC message to indicate that thenetwork device's configuration has changed, the configuration changenotification indicating a target of the edit operation, a type of theedit operation, and a value of the edit operation; and transmitting theconfiguration change notification to the network management system.

In an embodiment, said generating the configuration change notificationincludes: building a new datastore based on the received RPC message anda current datastore, the current datastore storing a currentconfiguration before the edit operation and the new datastore storing anew configuration after the edit operation; comparing the new datastorewith the current datastore; creating a difference datastore based on thecomparing, the difference datastore storing a configuration differencebetween the new configuration and the current configuration; andgenerating the configuration change notification based on theconfiguration difference.

In an embodiment, said generating the configuration change notificationbased on the configuration difference includes: setting the value of theedit operation based on the configuration difference.

In an embodiment, the type of the edit operation indicates deleting thetarget, and the value of the edit operation is null.

In an embodiment, the type of the edit operation indicates creating ormodifying the target, and the value of the edit operation indicates avalue the target of the edit operation is created or modified to have.

In a second aspect, a network device is provided for network managementbased on NETCONF protocol. The network device includes: a receiving unitconfigured to receive a RPC message from a network management system,the RPC message instructing the network device to perform an editoperation on the network device's configuration; a generating unitconfigured to generate a configuration change notification based on thereceived RPC message to indicate that the network device's configurationhas changed, the configuration change notification indicating a targetof the edit operation, a type of the edit operation, and a value of theedit operation; and a transmitting unit configured to transmit theconfiguration change notification to the network management system.

In a third aspect, a network device is provided for network managementbased on NETCONF protocol. The network device includes: a processor; anda memory storing instructions that when executed on the processor, causethe network device to: receive a RPC message from a network managementsystem, the RPC message instructing the network device to perform anedit operation on the network device's configuration; generate aconfiguration change notification based on the received RPC message toindicate that the network device's configuration has changed, theconfiguration change notification indicating a target of the editoperation, a type of the edit operation, and a value of the editoperation; and transmit the configuration change notification to thenetwork management system.

The above embodiments of the first aspect are also applicable for thesecond and third aspects.

With above embodiments of the present disclosure, the network device mayinform the network management system of all necessary information for anedit operation by adding a “value” element in the“netconf-config-change” notification, so that the network managementsystem can monitor the network device just based on the notificationwithout extra actions or tools. This may result in an improvement inefficiency and convenience of the network management.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features and advantages will be moreapparent from the following description of embodiments with reference tothe figures, in which:

FIG. 1 illustrates a structure diagram of the NETCONF protocol.

FIG. 2 depicts a tree structure of the “netconf-config-change”notification.

FIG. 3 is a schematic diagram illustrating an exemplary networkarchitecture for use in network management according to an embodiment ofthe present disclosure.

FIG. 4 illustrates an exemplary tree structure of the“netconf-config-change” notification according to an embodiment of thepresent disclosure.

FIG. 5 is a flowchart illustrating a method 500 used in a network devicefor network management based on the NETCONF protocol according to anembodiment of the present disclosure.

FIG. 6 is a schematic block diagram of a network device 600 according toan embodiment of the present disclosure.

FIG. 7 schematically shows an embodiment of an arrangement 700comprising at least one particular computer program product 708according to embodiments of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Hereinafter, the present disclosure is described with reference toembodiments shown in the attached drawings. However, it is to beunderstood that those descriptions are just provided for illustrativepurpose, rather than limiting the present disclosure. Further, in thefollowing, descriptions of known structures and techniques are omittedso as not to unnecessarily obscure the concept of the presentdisclosure.

FIG. 3 is a schematic diagram illustrating an exemplary networkarchitecture for use in network management according to an embodiment ofthe present disclosure. The network architecture involves a networkmanagement system 300, a network 310 and a network device 320. Thenetwork management system 300 and the network device 320 are examples ofa NETCONF client and a NETCONF server, respectively. The network 310 maybe either a wireless network such as the 5^(th) Generation (5G) network,or a wired network.

As shown in FIG. 3, there are two user sessions connected to the networkdevice 320 in the network management system 300. Session 1 isresponsible for configurations on the network device 320. Session 2 isresponsible for monitoring configuration operations on the networkdevice 320. For example, when Session 1 is to make a specificconfiguration on the network device 320 (e.g., this may be done byconfiguring the “edit-config” in the Yang module), a RPC message is sentfrom the network management system 300 to the network device 320 via thenetwork 310. In response to the RPC message, the configuration isapplied on the network device 320. Thereafter, the network device 320will generate and send a “netconf-config-change” notification to Session2 to indicate that the network device 320's configuration has changed.

According to an embodiment of the present disclosure, the“netconf-config-change” notification indicates a target of the editoperation, a type of the edit operation, and a value of the editoperation.

FIG. 4 illustrates an exemplary tree structure of the“netconf-config-change” notification according to an embodiment of thepresent disclosure.

As shown in FIG. 4, the “netconf-config-change” notification may havethree elements, i.e., “changed-by”, “datastore” and “edit”. The“changed-by” element and the “datastore” element are the same as thoseillustrated in FIG. 2, and thus detailed explanations thereof areomitted here. As illustrated, in addition to the leafs “Target” and“Operation,” the “edit” element further involves a new leaf, i.e.,“Value.” The leaf “Value” indicates a value of the edit operation, i.e.,a value configured for the edit operation.

An example of the YANG module definition according to the presentdisclosure may be presented as follows:

augment “/ncn:netconf-config-change/ncn:edit” { description “augment theedit list to report configuration changes”; leaf value { type string;description “if the operation is create or modify, it is the value whichis configured to. if the operation is delete, it is null”; } }

Assume that the edit operation is to create a specific target, e.g., A,as a value of “a”. In this case, the “Target” is A, the “Operation” is“create,” and then the “Value” is “a”. In other words, the editoperation is to create A as “a” on the network device 320.

With the “netconf-config-change” notification configured in this way,the network management system can monitor the network device just basedon the notification without extra actions or tools. This may result inan improvement in efficiency and convenience of the network management.

FIG. 5 is a flowchart illustrating a method 500 used in a network devicefor network management based on the NETCONF protocol according to anembodiment of the present disclosure. For example, the network devicemay be the network device 320 in FIG. 3.

At step S510, the network device receives a RPC message from a networkmanagement system. For example, the network management system may be thenetwork management system 300 in FIG. 3. The RPC message instructs thenetwork device to perform an edit operation on the network device'sconfiguration.

At step S520, the network device generates a configuration changenotification based on the received RPC message. The configuration changenotification indicates that the network device's configuration haschanged. The configuration change notification may specifically indicatea target of the edit operation, a type of the edit operation, and avalue of the edit operation. For example, the configuration changenotification may be “netconf-config-change” notification as illustratedin FIG. 4.

In an implementation, the type of the edit operation indicates deletingthe target, and then the value of the edit operation is null.

In another implementation, the type of the edit operation indicatescreating or modifying the target, and then the value of the editoperation indicates a value the target of the edit operation is createdor modified to have.

At step S530, the network device transmits the configuration changenotification to the network management system.

In an implementation, step S520 may include the following steps of:building a new datastore based on the received RPC message and a currentdatastore, the current datastore storing a current configuration beforethe edit operation and the new datastore storing a new configurationafter the edit operation; comparing the new datastore with the currentdatastore; creating a difference datastore based on the comparing, thedifference datastore storing a configuration difference between the newconfiguration and the current configuration; and generating theconfiguration change notification based on the configuration difference.As an example of this implementation, said generating the configurationchange notification based on the configuration difference may include:setting the value of the edit operation based on the configurationdifference.

FIG. 6 is a schematic block diagram of a network device 600 according toan embodiment of the present disclosure. The network device 600 is toperform network management based on the NETCONF protocol.

The part of the network device 600 which is most affected by theadaptation to the herein described method, e.g., the method 500, isillustrated as an arrangement 601, surrounded by a dashed line. Thenetwork device 600 and arrangement 601 are further configured tocommunicate with other entities such as a network management system viaa communication unit 602 which may be regarded as part of thearrangement 601. The communication unit 602 comprises means for wirelessor wired communication. The arrangement 601 or the network device 600may further comprise other functional units 604, such as functionalunits providing regular functions for a network device, and may furthercomprise one or more memories 603.

The arrangement 601 could be implemented, e.g., by one or more of: aprocessor or a microprocessor and adequate software and memory forstoring of the software, a Programmable Logic Device (PLD), or otherelectronic component(s) or processing circuitry configured to performthe actions described above, and illustrated, e.g., in FIG. 5. Thearrangement part of the network device 600 may be implemented and/ordescribed as follows.

Referring to FIG. 6, the network device 600 comprises a receiving unit610, a generating unit 620 and a transmitting unit 630.

The receiving unit 610 may be configured to receive a RPC message from anetwork management system. The RPC message instructs the network deviceto perform an edit operation on the network device's configuration.

The generating unit 620 may be configured to generate a configurationchange notification (e.g., the “netconf-config-change” notification asillustrated in FIG. 4) based on the received RPC message to indicatethat the network device's configuration has changed. The configurationchange notification may specifically indicate a target of the editoperation, a type of the edit operation, and a value of the editoperation.

In an implementation, the generating unit 620 may be further configuredto: build a new datastore based on the received RPC message and acurrent datastore, the current datastore storing a current configurationbefore the edit operation and the new datastore storing a newconfiguration after the edit operation; compare the new datastore withthe current datastore; create a difference datastore based on thecomparing, the difference datastore storing a configuration differencebetween the new configuration and the current configuration; andgenerate the configuration change notification based on theconfiguration difference. As an example of this implementation, saidgenerating the configuration change notification based on theconfiguration difference may include: setting the value of the editoperation based on the configuration difference.

The transmitting unit 630 may be configured to transmit theconfiguration change notification to the network management system.

In an implementation, the type of the edit operation indicates deletingthe target, and then the value of the edit operation is null.

In another implementation, the type of the edit operation indicatescreating or modifying the target, and the value of the edit operationindicates a value the target of the edit operation is created ormodified to have.

FIG. 7 schematically shows an embodiment of an arrangement 700comprising at least one particular computer program product 708according to embodiments of the present disclosure. The arrangement 700may be used in the network device 600 according to the presentdisclosure. Comprised in the arrangement 700 are here a processing unit706, e.g., with a Digital Signal Processor (DSP). The processing unit706 may be a single unit or a plurality of units to perform differentactions of procedures described herein. The arrangement 700 may alsocomprise an input unit 702 for receiving signals from other entities,and an output unit 704 for providing signal(s) to other entities. Theinput unit and the output unit may be arranged as an integrated entityor as illustrated in the example of FIG. 7.

Furthermore, the at least one computer program product 708 may be in theform of a non-volatile or volatile memory, e.g., an ElectricallyErasable Programmable Read-Only Memory (EEPROM), a flash memory and ahard drive. The computer program product 708 comprises a computerprogram 710, which comprises code/computer readable instructions, whichwhen executed by the processing unit 706 in the arrangement 700 causesthe arrangement 700 and/or the network device in which it is comprisedto perform the actions, e.g., of the procedure described earlier inconjunction with FIG. 5.

The computer program 710 may be configured as a computer program codestructured in computer program modules 710A-710D. Hence, in anexemplifying embodiment when the arrangement 700 is used in the networkdevice 600, the code in the computer program of the arrangement 700includes a receiving module 710A, for receiving a RPC message from anetwork management system. The RPC message instructs the network deviceto perform an edit operation on the network device's configuration. Thecode in the computer program 710 further includes a generating module710B, for generating a configuration change notification based on thereceived RPC message to indicate that the network device's configurationhas changed. The configuration change notification indicates a target ofthe edit operation, a type of the edit operation, and a value of theedit operation. The code in the computer program 710 may further includea transmitting module 710C, for transmitting the configuration changenotification to the network management system. The code in the computerprogram 710 may comprise further modules, illustrated as module 710D,e.g. for controlling and performing other related procedures associatedwith the network device's operations.

The computer program modules could essentially perform the actions ofthe flow illustrated in FIG. 5, to emulate the network device 600. Inother words, when the different computer program modules are executed inthe processing unit 706, they may correspond, e.g., to the units 610-630of FIG. 6.

Although the code means in the embodiments disclosed above inconjunction with FIG. 7 are implemented as computer program moduleswhich when executed in the processing unit causes the device to performthe actions described above in conjunction with the figures mentionedabove, at least one of the code means may in alternative embodiments beimplemented at least partly as hardware circuits.

The processor may be a single CPU (Central processing unit), but couldalso comprise two or more processing units. For example, the processormay include general purpose microprocessors; instruction set processorsand/or related chips sets and/or special purpose microprocessors such asApplication Specific Integrated Circuit (ASICs). The processor may alsocomprise board memory for caching purposes. The computer program may becarried by a computer program product connected to the processor. Thecomputer program product may comprise a computer readable medium onwhich the computer program is stored. For example, the computer programproduct may be a flash memory, a Random-access memory (RAM), a Read-OnlyMemory (ROM), or an EEPROM, and the computer program modules describedabove could in alternative embodiments be distributed on differentcomputer program products in the form of memories within the networkdevice.

The present disclosure is described above with reference to theembodiments thereof. However, those embodiments are provided just forillustrative purpose, rather than limiting the present disclosure. Thescope of the disclosure is defined by the attached claims as well asequivalents thereof. Those skilled in the art can make variousalternations and modifications without departing from the scope of thedisclosure, which all fall into the scope of the disclosure.

The invention claimed is:
 1. A method used in a network device fornetwork management based on NETwork CONFiguration (NETCONF) protocol,the method comprising: receiving a Remote Procedure Call (RPC) messagefrom a network management system, the RPC message instructing thenetwork device to perform an edit operation on a configuration of thenetwork device; generating a configuration change notification based onthe received RPC message to indicate that the configuration of thenetwork device has changed, the configuration change notificationindicating a target of the edit operation, a type of the edit operation,and a value of the edit operation, wherein said generating theconfiguration change notification comprises building a new datastorebased on the received RPC message and a current datastore, the currentdatastore storing a current configuration of the network device beforethe edit operation and the new datastore storing a new configuration ofthe network device after the edit operation; and transmitting theconfiguration change notification to the network management system. 2.The method according to claim 1, wherein said generating theconfiguration change notification further comprises: comparing the newdatastore with the current datastore; creating a difference datastorebased on the comparing, the difference datastore storing a configurationdifference between the new configuration and the current configuration;and generating the configuration change notification based on theconfiguration difference.
 3. The method according to claim 2, whereinsaid generating the configuration change notification based on theconfiguration difference comprises: setting the value of the editoperation based on the configuration difference.
 4. The method accordingto claim 1, wherein the type of the edit operation indicates deletingthe target, and the value of the edit operation is null.
 5. The methodaccording to claim 1, wherein the type of the edit operation indicatescreating or modifying the target, and the value of the edit operationindicates a value the target of the edit operation is created ormodified to have.
 6. A network device, device comprises a processor fornetwork management based on NETwork CONFiguration (NETCONF) protocol,the network device comprising: a receiving unit configured to receive aRemote Procedure Call (RPC) message from a network management system,the RPC message instructing the network device to perform an editoperation on a configuration of the network device; a generating unitconfigured to generate a configuration change notification based on thereceived RPC message to indicate that the configuration of the networkdevice has changed, the configuration change notification indicating atarget of the edit operation, a type of the edit operation, and a valueof the edit operation, wherein said generating unit is furtherconfigured to build a new datastore based on the received RPC messageand a current datastore, wherein the current datastore stores a currentconfiguration of the network device before the edit operation, andwherein the new datastore stores a new configuration of the networkdevice after the edit operation; and a transmitting unit configured totransmit the configuration change notification to the network managementsystem.
 7. The network device according to claim 6, wherein saidgenerating unit is further configured to: compare the new datastore withthe current datastore; create a difference datastore based on thecomparing, the difference datastore storing a configuration differencebetween the new configuration and the current configuration; andgenerate the configuration change notification based on theconfiguration difference.
 8. The network device according to claim 7,wherein said generating unit is further configured to: set the value ofthe edit operation based on the configuration difference to generate theconfiguration change notification.
 9. The network device according toclaim 6, wherein the type of the edit operation indicates deleting thetarget, and the value of the edit operation is null.
 10. The networkdevice according to claim 6, wherein the type of the edit operationindicates creating or modifying the target, and the value of the editoperation indicates a value the target of the edit operation is createdor modified to have.
 11. A network device for network management basedon NETwork CONFiguration (NETCONF) protocol, the network devicecomprising: a processor; and a memory storing instructions that whenexecuted on the processor, cause the network device to: receive a RemoteProcedure Call (RPC) message from a network management system, the RPCmessage instructing the network device to perform an edit operation on aconfiguration of the network device; generate a configuration changenotification based on the received RPC message to indicate that theconfiguration of the network device has changed, the configurationchange notification indicating a target of the edit operation, a type ofthe edit operation, and a value of the edit operation, wherein saidinstructions that when executed on the processor further cause thenetwork device to build a new datastore based on the received RPCmessage and a current datastore, wherein the current datastore stores acurrent configuration of the network device before the edit operation,and wherein the new datastore stores a new configuration of the networkdevice after the edit operation; and transmit the configuration changenotification to the network management system.
 12. The network deviceaccording to claim 11, wherein said instructions that when executed onthe processor further cause the network device to: compare the newdatastore with the current datastore; create a difference datastorebased on the comparing, wherein the difference datastore stores aconfiguration difference between the new configuration and the currentconfiguration; and generate the configuration change notification basedon the configuration difference.
 13. The network device according toclaim 12, wherein said instructions that when executed on the processorfurther cause the network device to: set the value of the edit operationbased on the configuration difference to generate the configurationchange notification.
 14. The network device according to claim 11,wherein the type of the edit operation indicates deleting the target,and the value of the edit operation is null.
 15. The network deviceaccording to claim 11, wherein the type of the edit operation indicatescreating or modifying the target, and the value of the edit operationindicates a value the target of the edit operation is created ormodified to have.
 16. A non-transitory computer readable medium storinginstructions that when executed by a processing unit of a network devicefor network management based on NETwork CONFiguration (NETCONF)protocol, cause the network device to: receive a Remote Procedure Call(RPC) message from a network management system, the RPC messageinstructing the network device to perform an edit operation on aconfiguration of the network device; generate a configuration changenotification based on the received RPC message to indicate that theconfiguration of the network device has changed, the configurationchange notification indicating a target of the edit operation, a type ofthe edit operation, and a value of the edit operation, wherein theinstructions that when executed by the processing unit of the networkdevice further cause the network device to build a new datastore basedon the received RPC message and a current datastore, wherein the currentdatastore stores a current configuration of the network device beforethe edit operation, and wherein the new datastore stores a newconfiguration of the network device after the edit operation; andtransmit the configuration change notification to the network managementsystem.